- Print
- DarkLight
Performs a partial update of article settings — only fields included in the request body are modified; omitted fields remain unchanged. Supports updating SEO metadata (slug, title, description), visibility flags (exclude from search, allow comments), tags, status indicators, related articles, and content type. Requires UpdateArticles permission and ACL access to the article.
All V3 endpoints require a Bearer token. Generate tokens in the Document360 portal under Settings > API Tokens. Tokens are project-scoped, require the customerApi scope, and do not expire by default. Tokens can be revoked at any time from the portal. Include the token in every request: Authorization: Bearer <your-token>. Alternatively, use the Authorize button below to sign in via OAuth2 Authorization Code flow with PKCE.
The unique identifier of the project. Retrieve project IDs from GET /v3/projects.
The unique identifier of the article. Retrieve article IDs from GET /v3/projects/{project_id}/articles.
ISO 639-1 language code (e.g., en, fr). Defaults to the project's primary language if omitted.
Updated article settings.
Updates the SEO title, meta description, and tags for better search engine visibility.
{
"slug": "getting-started-with-single-sign-on",
"seo_title": "SSO Setup Guide - Product Documentation",
"description": "Step-by-step instructions for configuring single sign-on with SAML or OIDC providers.",
"allow_comments": null,
"show_table_of_contents": null,
"tags": [
"SSO",
"authentication",
"SAML",
"OIDC"
],
"status_indicator": null,
"status_indicator_expiry_date": null,
"exclude_from_search": null,
"exclude_from_ai_search": null,
"exclude_from_external_search": null,
"related_articles": null,
"content_type": null,
"is_acknowledgement_enabled": null
}Marks the article as updated and links related articles for cross-referencing.
{
"slug": null,
"seo_title": null,
"description": null,
"allow_comments": null,
"show_table_of_contents": null,
"tags": null,
"status_indicator": "updated",
"status_indicator_expiry_date": "2025-12-31T23:59:59Z",
"exclude_from_search": null,
"exclude_from_ai_search": null,
"exclude_from_external_search": null,
"related_articles": [
"c5d6e7f8-9a0b-1c2d-3e4f-5a6b7c8d9e0f",
"e7f8a9b0-1c2d-3e4f-5a6b-7c8d9e0f1a2b"
],
"content_type": null,
"is_acknowledgement_enabled": null
}Request to update article settings.
The custom SEO title for search engines.
The meta description for search engines.
Whether reader comments are allowed on the article.
Whether the table of contents is displayed.
The list of tags to associate with the article.
The status indicator badge to display on the article. Possible values: 0 = None, 1 = New, 2 = Updated, 3 = Custom.
The expiry date for the status indicator badge. Only applicable when StatusIndicator is set.
Whether to exclude the article from internal search results.
Whether to exclude the article from AI-powered search.
Whether to exclude the article from external search engine indexing.
The list of related article identifiers to link. Supply article IDs as strings; the corresponding GET response returns enriched objects with title, slug, and visibility. Retrieve article IDs from GET /v3/projects/{projectId}/articles.
The editor content type for the article. Possible values: 0 = Markdown, 1 = Wysiwyg (rich text), 2 = Block.
Whether reader acknowledgement is required for this article.
Article settings updated successfully.
The article settings have been updated. Only the fields included in the request were modified.
{
"data": {
"slug": "getting-started-with-single-sign-on",
"seo_title": "SSO Setup Guide - Product Documentation",
"description": "Step-by-step instructions for configuring single sign-on with SAML or OIDC providers.",
"allow_comments": true,
"show_table_of_contents": true,
"featured_image_url": null,
"tags": [
"SSO",
"authentication",
"SAML",
"OIDC"
],
"status_indicator": "updated",
"status_indicator_expiry_date": "2025-12-31T23:59:59Z",
"exclude_from_search": false,
"exclude_from_ai_search": false,
"exclude_from_external_search": false,
"related_articles": [
{
"id": "c5d6e7f8-9a0b-1c2d-3e4f-5a6b7c8d9e0f",
"title": "Configuring SAML Identity Providers",
"hidden": false,
"slug": "configuring-saml-identity-providers"
}
],
"is_acknowledgement_enabled": false,
"url": "https://docs.example.com/en/articles/getting-started-with-single-sign-on"
},
"success": true,
"request_id": "req_abc123def456",
"errors": null,
"warnings": null
}Generic API response wrapper containing typed data.
Response data payload.
The URL slug for the article.
The custom SEO title for search engines.
The meta description for search engines.
Whether reader comments are allowed on the article.
Whether the table of contents is displayed.
The URL of the featured image for the article. For private or mixed-visibility projects, a time-limited SAS token is automatically appended. Read-only; the featured image can only be set via the Document360 portal.
The list of tags associated with the article.
The status indicator badge shown on the article. Possible values: 0 = None, 1 = New, 2 = Updated, 3 = Custom.
The expiry date for the status indicator badge. Only applicable when StatusIndicator is set.
Whether the article is excluded from internal search results.
Whether the article is excluded from AI-powered search.
Whether the article is excluded from external search engine indexing.
The list of related articles linked to this article, returned as enriched objects. When updating via PATCH, supply only article IDs as strings.
A related article linked from another article's settings.
The unique identifier of the related article.
The title of the related article.
Whether the related article is hidden from readers.
The URL slug of the related article.
Whether reader acknowledgement is required for this article.
The full URL of the article.
Whether the API request was successful.
Unique identifier for request tracing and correlation.
List of errors if the request failed.
Represents an error returned by the API.
Machine-readable error code (e.g. VALIDATION_ERROR, RESOURCE_NOT_FOUND).
Human-readable error message.
The request field that caused the error, if applicable.
Additional context about the error.
List of non-fatal warnings from the request.
Represents a non-fatal warning from the API.
Machine-readable warning code.
Human-readable warning message.
The request body is malformed or contains invalid JSON.
RFC 7807 Problem Details response for V3 API errors. Content-Type: application/problem+json
URI reference identifying the error type (links to documentation).
Short human-readable summary of the error type.
HTTP status code.
Human-readable explanation specific to this occurrence.
URI of the request that generated the error.
Request trace identifier for correlation.
Structured list of specific errors (extension field).
Represents an error returned by the API.
Machine-readable error code (e.g. VALIDATION_ERROR, RESOURCE_NOT_FOUND).
Human-readable error message.
The request field that caused the error, if applicable.
Additional context about the error.
Non-fatal warnings (extension field).
Represents a non-fatal warning from the API.
Machine-readable warning code.
Human-readable warning message.
Authentication token is missing or invalid.
Authentication token is missing or invalid.
{
"type": "https://developer.document360.com/errors/unauthorized",
"title": "Unauthorized.",
"status": 401,
"detail": "The authentication token is missing or has expired.",
"instance": null,
"trace_id": "req_abc123def456",
"errors": [
{
"code": "UNAUTHORIZED",
"message": "Bearer token is missing or invalid.",
"field": null,
"details": null
}
],
"warnings": null
}RFC 7807 Problem Details response for V3 API errors. Content-Type: application/problem+json
URI reference identifying the error type (links to documentation).
Short human-readable summary of the error type.
HTTP status code.
Human-readable explanation specific to this occurrence.
URI of the request that generated the error.
Request trace identifier for correlation.
Structured list of specific errors (extension field).
Represents an error returned by the API.
Machine-readable error code (e.g. VALIDATION_ERROR, RESOURCE_NOT_FOUND).
Human-readable error message.
The request field that caused the error, if applicable.
Additional context about the error.
Non-fatal warnings (extension field).
Represents a non-fatal warning from the API.
Machine-readable warning code.
Human-readable warning message.
Article not found.
The requested resource was not found.
{
"type": "https://developer.document360.com/errors/not-found",
"title": "Not Found.",
"status": 404,
"detail": "The requested resource does not exist or has been deleted.",
"instance": null,
"trace_id": "req_abc123def456",
"errors": [
{
"code": "RESOURCE_NOT_FOUND",
"message": "The requested resource was not found.",
"field": null,
"details": null
}
],
"warnings": null
}RFC 7807 Problem Details response for V3 API errors. Content-Type: application/problem+json
URI reference identifying the error type (links to documentation).
Short human-readable summary of the error type.
HTTP status code.
Human-readable explanation specific to this occurrence.
URI of the request that generated the error.
Request trace identifier for correlation.
Structured list of specific errors (extension field).
Represents an error returned by the API.
Machine-readable error code (e.g. VALIDATION_ERROR, RESOURCE_NOT_FOUND).
Human-readable error message.
The request field that caused the error, if applicable.
Additional context about the error.
Non-fatal warnings (extension field).
Represents a non-fatal warning from the API.
Machine-readable warning code.
Human-readable warning message.
Validation failed.
The request body contains invalid data.
{
"type": "https://developer.document360.com/errors/validation-error",
"title": "Unprocessable Entity.",
"status": 422,
"detail": "One or more fields failed validation.",
"instance": null,
"trace_id": "req_abc123def456",
"errors": [
{
"code": "VALIDATION_ERROR",
"message": "This field is required.",
"field": "title",
"details": null
}
],
"warnings": null
}RFC 7807 Problem Details response for V3 API errors. Content-Type: application/problem+json
URI reference identifying the error type (links to documentation).
Short human-readable summary of the error type.
HTTP status code.
Human-readable explanation specific to this occurrence.
URI of the request that generated the error.
Request trace identifier for correlation.
Structured list of specific errors (extension field).
Represents an error returned by the API.
Machine-readable error code (e.g. VALIDATION_ERROR, RESOURCE_NOT_FOUND).
Human-readable error message.
The request field that caused the error, if applicable.
Additional context about the error.
Non-fatal warnings (extension field).
Represents a non-fatal warning from the API.
Machine-readable warning code.
Human-readable warning message.
Rate limit exceeded. Retry after the duration specified in the Retry-After header.
Rate limit exceeded.
{
"type": "https://developer.document360.com/errors/too-many-requests",
"title": "Too Many Requests.",
"status": 429,
"detail": "Rate limit exceeded. Retry after the duration specified in the Retry-After header.",
"instance": null,
"trace_id": "req_abc123def456",
"errors": [
{
"code": "TOO_MANY_REQUESTS",
"message": "Rate limit exceeded. Retry after the duration specified in the Retry-After header.",
"field": null,
"details": null
}
],
"warnings": null
}RFC 7807 Problem Details response for V3 API errors. Content-Type: application/problem+json
URI reference identifying the error type (links to documentation).
Short human-readable summary of the error type.
HTTP status code.
Human-readable explanation specific to this occurrence.
URI of the request that generated the error.
Request trace identifier for correlation.
Structured list of specific errors (extension field).
Represents an error returned by the API.
Machine-readable error code (e.g. VALIDATION_ERROR, RESOURCE_NOT_FOUND).
Human-readable error message.
The request field that caused the error, if applicable.
Additional context about the error.
Non-fatal warnings (extension field).
Represents a non-fatal warning from the API.
Machine-readable warning code.
Human-readable warning message.
An unexpected server error occurred.
Unexpected server error.
{
"type": "https://developer.document360.com/errors/internal-error",
"title": "Internal Server Error.",
"status": 500,
"detail": "An unexpected error occurred. Please try again or contact support.",
"instance": null,
"trace_id": "req_abc123def456",
"errors": [
{
"code": "INTERNAL_SERVER_ERROR",
"message": "An unexpected error occurred.",
"field": null,
"details": null
}
],
"warnings": null
}RFC 7807 Problem Details response for V3 API errors. Content-Type: application/problem+json
URI reference identifying the error type (links to documentation).
Short human-readable summary of the error type.
HTTP status code.
Human-readable explanation specific to this occurrence.
URI of the request that generated the error.
Request trace identifier for correlation.
Structured list of specific errors (extension field).
Represents an error returned by the API.
Machine-readable error code (e.g. VALIDATION_ERROR, RESOURCE_NOT_FOUND).
Human-readable error message.
The request field that caused the error, if applicable.
Additional context about the error.
Non-fatal warnings (extension field).
Represents a non-fatal warning from the API.
Machine-readable warning code.
Human-readable warning message.
